Fix appeal flow wiring: incidents + restriction messages#16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two fixes so the appeal flow actually works at runtime.
runtimeAssemblysetWeb.AuditServicebut never the top-levelAuditServicefield, somakeTelegramListener'sif a.AuditService != nilwas always false. Result:IncidentCreatorwas never attached to the listener, no audit incident was created from the moderation pipeline, andensureIncidentalways returned 0 — so the "Обжаловать" button was never attached to warn/ban messages. WiredAuditService: auditSvcinto the assembly struct (pre-existing bug, surfaced by the appeal feature).postBanGroupMessageskippedpc.outcome.Restrict, so temporary mutes (early strikes, soft-ban mode) posted no group message and no appeal button. It now posts for restrictions too, with text🔇 Пользователь ограничен за спам(vs🚫 Пользователь забанен за спамfor a permanent ban). Still skipped for channel bans and dry/training runs.